Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 133368d55e3c7f46498af1018c67d5742c9932882205951aba9443ac96302d8a

Tx prefix hash: 57dba775e289a057c73b9a6394dcf14c9cfaedba77d2199cde3ab039444585f6
Tx public key: 379ea6a002e78bd7acdd1b09dafddd3ebeb079897ad3fd5f65b938f22825d1fb
Timestamp: 1724876635 Timestamp [UCT]: 2024-08-28 20:23:55 Age [y:d:h:m:s]: 00:218:02:58:10
Block: 1097980 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155750 RingCT/type: yes/0
Extra: 01379ea6a002e78bd7acdd1b09dafddd3ebeb079897ad3fd5f65b938f22825d1fb02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d359990b948a523c6a234a698c4a0f4bf4bbe8d892a7d7d757b0d1157c8b02c4 0.600000000000 1573537 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": 1097990, "vin": [ { "gen": { "height": 1097980 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d359990b948a523c6a234a698c4a0f4bf4bbe8d892a7d7d757b0d1157c8b02c4" } } ], "extra": [ 1, 55, 158, 166, 160, 2, 231, 139, 215, 172, 221, 27, 9, 218, 253, 221, 62, 190, 176, 121, 137, 122, 211, 253, 95, 101, 185, 56, 242, 40, 37, 209, 251, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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