Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5146d8c45445738067478b403b5da62a5523cbc275ec46d27d737c477fe7f33b

Tx prefix hash: b47d46446cddf480e8b3dc55bc972e9826c5bc236fe9658d5d503d614f16d358
Tx public key: cf6b2c18fa32483793b7f51d6aa4562a4d7a71126578bb44c7060e829a814ce5
Timestamp: 1580112032 Timestamp [UCT]: 2020-01-27 08:00:32 Age [y:d:h:m:s]: 04:338:03:04:02
Block: 53671 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1132008 RingCT/type: yes/0
Extra: 01cf6b2c18fa32483793b7f51d6aa4562a4d7a71126578bb44c7060e829a814ce5021100000002391a8d0e000000000000000000

1 output(s) for total of 407.536512557000 dcy

stealth address amount amount idx
00: cdf47e977a7004d73824fc4c5fafcedf101e572cacc20f4da1be6b3419572fe3 407.536512557000 99511 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": 53681, "vin": [ { "gen": { "height": 53671 } } ], "vout": [ { "amount": 407536512557, "target": { "key": "cdf47e977a7004d73824fc4c5fafcedf101e572cacc20f4da1be6b3419572fe3" } } ], "extra": [ 1, 207, 107, 44, 24, 250, 50, 72, 55, 147, 183, 245, 29, 106, 164, 86, 42, 77, 122, 113, 18, 101, 120, 187, 68, 199, 6, 14, 130, 154, 129, 76, 229, 2, 17, 0, 0, 0, 2, 57, 26, 141, 14, 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