Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 87f0921f8c4cf3839de29706f05dadc71650086b171c28dca2770e3ceef5165c

Tx prefix hash: c261ab9606030c9f5c310dcfe06afa43ede7dff085617d13eea8cc6f7a0f7405
Tx public key: 1f6d8eae65f0e5c6ab7fdd5fd126429d5fb8e25bfac9a21094dd223ed1a9b00f
Timestamp: 1725011223 Timestamp [UCT]: 2024-08-30 09:47:03 Age [y:d:h:m:s]: 00:259:22:17:20
Block: 1099096 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185658 RingCT/type: yes/0
Extra: 011f6d8eae65f0e5c6ab7fdd5fd126429d5fb8e25bfac9a21094dd223ed1a9b00f02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9dd1c5862fcf09d1bb22ef77766bbf1b03f27dcd34c7b843e7542a1fe6d4953e 0.600000000000 1575023 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1099106, "vin": [ { "gen": { "height": 1099096 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9dd1c5862fcf09d1bb22ef77766bbf1b03f27dcd34c7b843e7542a1fe6d4953e" } } ], "extra": [ 1, 31, 109, 142, 174, 101, 240, 229, 198, 171, 127, 221, 95, 209, 38, 66, 157, 95, 184, 226, 91, 250, 201, 162, 16, 148, 221, 34, 62, 209, 169, 176, 15, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8