Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c1fa628c671a3f15126e64c19b968c7a7ebf2e85c27d7086ed008ac3d3db21f

Tx prefix hash: 05e748b344f049922ec75fde641c7aebe216873a524b4f2e77db8d1bc8fefaeb
Tx public key: 8c83fc2c897aa8df9a5f5427be529f972ce1171189a01b04ab0d768fd3e13fa1
Timestamp: 1735623418 Timestamp [UCT]: 2024-12-31 05:36:58 Age [y:d:h:m:s]: 00:304:16:32:36
Block: 1186947 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215267 RingCT/type: yes/0
Extra: 018c83fc2c897aa8df9a5f5427be529f972ce1171189a01b04ab0d768fd3e13fa1021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 83f3ee6b99910b28291d6189fbf617a12ce1d02e83e0477e3e03f01b16c12f27 0.600000000000 1673432 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": 1186957, "vin": [ { "gen": { "height": 1186947 } } ], "vout": [ { "amount": 600000000, "target": { "key": "83f3ee6b99910b28291d6189fbf617a12ce1d02e83e0477e3e03f01b16c12f27" } } ], "extra": [ 1, 140, 131, 252, 44, 137, 122, 168, 223, 154, 95, 84, 39, 190, 82, 159, 151, 44, 225, 23, 17, 137, 160, 27, 4, 171, 13, 118, 143, 211, 225, 63, 161, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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