Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c53a1ac8eab873a4f1fe589ebe37109517011dacc2ba714149964a898a768763

Tx prefix hash: 3f02e51226eecefbf5265e9e69277abce7a41c062ef4392869a0a4d651c4c316
Tx public key: f2c8815d0e7eb57a2c64fa0d7069038ce7430b6749b1bb3e41459b55f84d6538
Timestamp: 1723732473 Timestamp [UCT]: 2024-08-15 14:34:33 Age [y:d:h:m:s]: 00:222:19:06:53
Block: 1088503 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159093 RingCT/type: yes/0
Extra: 01f2c8815d0e7eb57a2c64fa0d7069038ce7430b6749b1bb3e41459b55f84d6538021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 979cbe95f0b38ce50df783cd077267daa337b1c69a388f06234f4d23c9d2aa80 0.600000000000 1563120 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": 1088513, "vin": [ { "gen": { "height": 1088503 } } ], "vout": [ { "amount": 600000000, "target": { "key": "979cbe95f0b38ce50df783cd077267daa337b1c69a388f06234f4d23c9d2aa80" } } ], "extra": [ 1, 242, 200, 129, 93, 14, 126, 181, 122, 44, 100, 250, 13, 112, 105, 3, 140, 231, 67, 11, 103, 73, 177, 187, 62, 65, 69, 155, 85, 248, 77, 101, 56, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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