Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e2fb18665c32a8d19d94097cfa776da6bf685c8493bd4539bc98f8ae7437db2

Tx prefix hash: 1bc469b0da0728b15b96efac245db537b5d2b34c4d0d6372f6cff4ae44019ae0
Tx public key: 2394a6224f1928d87bc1138ee0ab8a8b011afb3d11e24f16333808f60c7245b2
Timestamp: 1636667538 Timestamp [UCT]: 2021-11-11 21:52:18 Age [y:d:h:m:s]: 03:167:01:51:03
Block: 372374 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 897824 RingCT/type: yes/0
Extra: 012394a6224f1928d87bc1138ee0ab8a8b011afb3d11e24f16333808f60c7245b202110000000a42b3953e000000000000000000

1 output(s) for total of 35.823725546000 dcy

stealth address amount amount idx
00: c03f872c174bcd53ac56b04930bfbea3447bec2393301bb1f22e5e309ccf8a43 35.823725546000 754334 of 0

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": 372384, "vin": [ { "gen": { "height": 372374 } } ], "vout": [ { "amount": 35823725546, "target": { "key": "c03f872c174bcd53ac56b04930bfbea3447bec2393301bb1f22e5e309ccf8a43" } } ], "extra": [ 1, 35, 148, 166, 34, 79, 25, 40, 216, 123, 193, 19, 142, 224, 171, 138, 139, 1, 26, 251, 61, 17, 226, 79, 22, 51, 56, 8, 246, 12, 114, 69, 178, 2, 17, 0, 0, 0, 10, 66, 179, 149, 62, 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