Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 085da62651a6e25b78e9912b99df88c897f12b72275c8d26314c9fc3aec9ff2f

Tx prefix hash: 3bae36cc14aac2506e50c18d8559330fe85e27b061715644a0f5ffeed8a332ab
Tx public key: aa901063fff551e2b8f2de3169a6861ac53adcb540fd7ba073729b49dfc0643d
Timestamp: 1673163213 Timestamp [UCT]: 2023-01-08 07:33:33 Age [y:d:h:m:s]: 01:317:09:01:48
Block: 670108 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 487837 RingCT/type: yes/0
Extra: 01aa901063fff551e2b8f2de3169a6861ac53adcb540fd7ba073729b49dfc0643d02110000000c52542ceb000000000000000000

1 output(s) for total of 3.695336384000 dcy

stealth address amount amount idx
00: 5e564ba108803fe4171d785e6e6790aa5eaa1a431d024091dc4c2675c882d21a 3.695336384000 1111481 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": 670118, "vin": [ { "gen": { "height": 670108 } } ], "vout": [ { "amount": 3695336384, "target": { "key": "5e564ba108803fe4171d785e6e6790aa5eaa1a431d024091dc4c2675c882d21a" } } ], "extra": [ 1, 170, 144, 16, 99, 255, 245, 81, 226, 184, 242, 222, 49, 105, 166, 134, 26, 197, 58, 220, 181, 64, 253, 123, 160, 115, 114, 155, 73, 223, 192, 100, 61, 2, 17, 0, 0, 0, 12, 82, 84, 44, 235, 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