Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2a84ea6a1e3c35eb2bf1c64fa8a603b644dd33f04bf164cfe620445d6961e50

Tx prefix hash: 859eee71daeee80e4f46fcf4a5c02f37479dca530e489b3c72d424ffa9dc50ce
Tx public key: e5fb26a2da73547dc03d02965a20473bc3e5a7ce75d4fcc9b3a139c5f592334f
Timestamp: 1750498202 Timestamp [UCT]: 2025-06-21 09:30:02 Age [y:d:h:m:s]: 00:148:11:56:42
Block: 1309657 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103980 RingCT/type: yes/0
Extra: 01e5fb26a2da73547dc03d02965a20473bc3e5a7ce75d4fcc9b3a139c5f592334f02110000000201491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 05b4b73ec176e78e2ae6d61e8c15ddb78676f2489e328b6bf31c1e20148292fe 0.600000000000 1797274 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": 1309667, "vin": [ { "gen": { "height": 1309657 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05b4b73ec176e78e2ae6d61e8c15ddb78676f2489e328b6bf31c1e20148292fe" } } ], "extra": [ 1, 229, 251, 38, 162, 218, 115, 84, 125, 192, 61, 2, 150, 90, 32, 71, 59, 195, 229, 167, 206, 117, 212, 252, 201, 179, 161, 57, 197, 245, 146, 51, 79, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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