Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2679717d3de38b3c26f9787723ab3bc693fe25ded1f7af7d4393f47addd38498

Tx prefix hash: 630f49d2514d1b1bf445406584a8e3efc391d986214c74a7e214324f31922ba2
Tx public key: ca5ff78c98f1ed39783358a2c9d5b475cf76317249a6bde0ddca0613c1961d8d
Timestamp: 1725434653 Timestamp [UCT]: 2024-09-04 07:24:13 Age [y:d:h:m:s]: 00:208:19:57:32
Block: 1102609 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149087 RingCT/type: yes/0
Extra: 01ca5ff78c98f1ed39783358a2c9d5b475cf76317249a6bde0ddca0613c1961d8d02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6d458d68fba6c52c5086d7e4ee4ccfad34763d2311cfb11e2e8a2b12f0754b76 0.600000000000 1579116 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": 1102619, "vin": [ { "gen": { "height": 1102609 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d458d68fba6c52c5086d7e4ee4ccfad34763d2311cfb11e2e8a2b12f0754b76" } } ], "extra": [ 1, 202, 95, 247, 140, 152, 241, 237, 57, 120, 51, 88, 162, 201, 213, 180, 117, 207, 118, 49, 114, 73, 166, 189, 224, 221, 202, 6, 19, 193, 150, 29, 141, 2, 17, 0, 0, 0, 1, 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