Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 15ef3b5495bf34b8bb3fe8313a88fe8f5ccd44fa5e6bef7eac70a5fc46306364

Tx prefix hash: b27d044683deb5f55e3b3879925a41f641c248e31eaa270f507374d4173aa62c
Tx public key: 3f090fc259f1ff7263e4b44f2a917186dbc3eafe7cbb4bd57e64a6493e01c47a
Timestamp: 1750358179 Timestamp [UCT]: 2025-06-19 18:36:19 Age [y:d:h:m:s]: 00:221:21:22:48
Block: 1308536 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156322 RingCT/type: yes/0
Extra: 013f090fc259f1ff7263e4b44f2a917186dbc3eafe7cbb4bd57e64a6493e01c47a021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fc782199e19eb53aee9dc1cd413b6aaa2d18808ffd43daae427e17ed9649f033 0.600000000000 1796149 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": 1308546, "vin": [ { "gen": { "height": 1308536 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc782199e19eb53aee9dc1cd413b6aaa2d18808ffd43daae427e17ed9649f033" } } ], "extra": [ 1, 63, 9, 15, 194, 89, 241, 255, 114, 99, 228, 180, 79, 42, 145, 113, 134, 219, 195, 234, 254, 124, 187, 75, 213, 126, 100, 166, 73, 62, 1, 196, 122, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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