Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f3dcb1e93139c7c819aac5d790cf2e69e3dfb73582a0c92c387711937e6990a

Tx prefix hash: 0bf65bf8250c87a4de045cf05986035ad1b81e2d4bf1f00972f821007f0a19a2
Tx public key: f0e48cbce90050c0e84bbfba8f12a4bcf65617d63a74fc16210baabaa256287a
Timestamp: 1743788760 Timestamp [UCT]: 2025-04-04 17:46:00 Age [y:d:h:m:s]: 00:230:03:58:41
Block: 1254278 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162233 RingCT/type: yes/0
Extra: 01f0e48cbce90050c0e84bbfba8f12a4bcf65617d63a74fc16210baabaa256287a0211000000014060f6d2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac141df0a7817152f854f9d1dd30a457a1e1e8fcace7a9c1c8572e03fac58069 0.600000000000 1741359 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": 1254288, "vin": [ { "gen": { "height": 1254278 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac141df0a7817152f854f9d1dd30a457a1e1e8fcace7a9c1c8572e03fac58069" } } ], "extra": [ 1, 240, 228, 140, 188, 233, 0, 80, 192, 232, 75, 191, 186, 143, 18, 164, 188, 246, 86, 23, 214, 58, 116, 252, 22, 33, 11, 170, 186, 162, 86, 40, 122, 2, 17, 0, 0, 0, 1, 64, 96, 246, 210, 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