Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f86e76c0ba11a47def57e5f11a7e317bf4f338a826029cfb8f2d61ecc225ba4

Tx prefix hash: a7f6a9283dee6172a77497d81c6bc57c7ee7ce3260804204132646fd9a0464f6
Tx public key: b08be8d202a47841d5330047d76f8017d22650a496056f9199a5a51524f2cff4
Timestamp: 1704351678 Timestamp [UCT]: 2024-01-04 07:01:18 Age [y:d:h:m:s]: 01:126:06:42:06
Block: 927825 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351366 RingCT/type: yes/0
Extra: 01b08be8d202a47841d5330047d76f8017d22650a496056f9199a5a51524f2cff4021100000002e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 218b0afd344e90a50345c3cf790aef55b9e4f9c2293abcab59950b6abd0a65a5 0.600000000000 1385661 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": 927835, "vin": [ { "gen": { "height": 927825 } } ], "vout": [ { "amount": 600000000, "target": { "key": "218b0afd344e90a50345c3cf790aef55b9e4f9c2293abcab59950b6abd0a65a5" } } ], "extra": [ 1, 176, 139, 232, 210, 2, 164, 120, 65, 213, 51, 0, 71, 215, 111, 128, 23, 210, 38, 80, 164, 150, 5, 111, 145, 153, 165, 165, 21, 36, 242, 207, 244, 2, 17, 0, 0, 0, 2, 224, 133, 50, 182, 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