Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5db12edba6c188eb69921f3cc2f1d63c38ae0e93305d8703537f3a363cbe208

Tx prefix hash: bf7fb366723244a346dde9bb0501c95bcff2c4898394e7ed4132cdf5c7ac2ae9
Tx public key: 4092607f15f65fadc582cd7a20b6035b16645155dda52e681e5dc93bdd8e6e24
Timestamp: 1721589627 Timestamp [UCT]: 2024-07-21 19:20:27 Age [y:d:h:m:s]: 00:296:17:39:40
Block: 1070725 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212040 RingCT/type: yes/0
Extra: 014092607f15f65fadc582cd7a20b6035b16645155dda52e681e5dc93bdd8e6e2402110000001291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7fdc95b408ef5cb5f710007fd584cf7e99df0087452959aa0d76a24c00567a2d 0.600000000000 1542678 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": 1070735, "vin": [ { "gen": { "height": 1070725 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7fdc95b408ef5cb5f710007fd584cf7e99df0087452959aa0d76a24c00567a2d" } } ], "extra": [ 1, 64, 146, 96, 127, 21, 246, 95, 173, 197, 130, 205, 122, 32, 182, 3, 91, 22, 100, 81, 85, 221, 165, 46, 104, 30, 93, 201, 59, 221, 142, 110, 36, 2, 17, 0, 0, 0, 18, 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