Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b454b074049d7e795fe88038f707694d3d39bd3c3a746ecfac967154fc2fb719

Tx prefix hash: b38c334dbc9a9b3635d4c21de6b0fcb840581cf46071072fe2399170d4e9d9bd
Tx public key: 54e52306d6abde90ab692d9704c6ed058f8cc5b75cfd2146b1d0a4db630631d1
Timestamp: 1677474301 Timestamp [UCT]: 2023-02-27 05:05:01 Age [y:d:h:m:s]: 02:047:01:28:44
Block: 705877 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 555241 RingCT/type: yes/0
Extra: 0154e52306d6abde90ab692d9704c6ed058f8cc5b75cfd2146b1d0a4db630631d1021100000001faf35c9c000000000000000000

1 output(s) for total of 2.812783982000 dcy

stealth address amount amount idx
00: 74982e36b28fc3fcdc028f819cc29af17e630c7d607091035b3516643a351000 2.812783982000 1149590 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": 705887, "vin": [ { "gen": { "height": 705877 } } ], "vout": [ { "amount": 2812783982, "target": { "key": "74982e36b28fc3fcdc028f819cc29af17e630c7d607091035b3516643a351000" } } ], "extra": [ 1, 84, 229, 35, 6, 214, 171, 222, 144, 171, 105, 45, 151, 4, 198, 237, 5, 143, 140, 197, 183, 92, 253, 33, 70, 177, 208, 164, 219, 99, 6, 49, 209, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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