Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9df9b6017519d7f1df8ab6332fe30da25c1a04b355e7407ef825b00eac9504f6

Tx prefix hash: e268e8ab095a24d64fa581a725a63b5356f83bb29a1eedcac9e2bf0f50d444ce
Tx public key: 946b4d768b6755dcecb320b0dc232b95557e9f694ecdbcf18c3ac87f43e8697d
Timestamp: 1748317609 Timestamp [UCT]: 2025-05-27 03:46:49 Age [y:d:h:m:s]: 00:178:00:17:19
Block: 1291781 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124911 RingCT/type: yes/0
Extra: 01946b4d768b6755dcecb320b0dc232b95557e9f694ecdbcf18c3ac87f43e8697d021100000002523560da000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 44d49bab3e5deef6d7e1cc754bb6b8dc065264f0d4239e51f6849c0129d8f943 0.600000000000 1779252 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": 1291791, "vin": [ { "gen": { "height": 1291781 } } ], "vout": [ { "amount": 600000000, "target": { "key": "44d49bab3e5deef6d7e1cc754bb6b8dc065264f0d4239e51f6849c0129d8f943" } } ], "extra": [ 1, 148, 107, 77, 118, 139, 103, 85, 220, 236, 179, 32, 176, 220, 35, 43, 149, 85, 126, 159, 105, 78, 205, 188, 241, 140, 58, 200, 127, 67, 232, 105, 125, 2, 17, 0, 0, 0, 2, 82, 53, 96, 218, 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