Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ef33423dce8ef805abf762934970eeccdb4073242175379a89120b148869fae

Tx prefix hash: 2bf7f24d1025269749b7cfea8ad85adc8e91212d7857a1ed3047a045413e2a53
Tx public key: 367dfd5dfdf742d5ed710ca47003eef092e8b702d7c57b67238df8bfdff165dd
Timestamp: 1636028357 Timestamp [UCT]: 2021-11-04 12:19:17 Age [y:d:h:m:s]: 03:174:10:26:24
Block: 367172 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 903003 RingCT/type: yes/0
Extra: 01367dfd5dfdf742d5ed710ca47003eef092e8b702d7c57b67238df8bfdff165dd0211000000016a2c97e6000000000000000000

1 output(s) for total of 37.274747946000 dcy

stealth address amount amount idx
00: 15e14230d4e41093557f66d11d6d16d4e0a6a49a86f2bd98f5e3c1706d72ef12 37.274747946000 745090 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": 367182, "vin": [ { "gen": { "height": 367172 } } ], "vout": [ { "amount": 37274747946, "target": { "key": "15e14230d4e41093557f66d11d6d16d4e0a6a49a86f2bd98f5e3c1706d72ef12" } } ], "extra": [ 1, 54, 125, 253, 93, 253, 247, 66, 213, 237, 113, 12, 164, 112, 3, 238, 240, 146, 232, 183, 2, 215, 197, 123, 103, 35, 141, 248, 191, 223, 241, 101, 221, 2, 17, 0, 0, 0, 1, 106, 44, 151, 230, 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