Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc7dfa3a590279b1cb1c988fc1fb8b2509a2981c5b1b395bf76eef41265d17e6

Tx prefix hash: 926128778066c46698f3e4eaa6a95dae66583976a7c98f2d9863df162107ba82
Tx public key: b7446faacf03a9cb79305b352d5100860329936eb4e92133c649f1584e5ee082
Timestamp: 1695905298 Timestamp [UCT]: 2023-09-28 12:48:18 Age [y:d:h:m:s]: 01:176:01:51:38
Block: 858006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 386887 RingCT/type: yes/0
Extra: 01b7446faacf03a9cb79305b352d5100860329936eb4e92133c649f1584e5ee082021100000006faf35c9c000000000000000000

1 output(s) for total of 0.881190876000 dcy

stealth address amount amount idx
00: 2048d7fd3475edb8f62cf9b4912270cfd011e41c0b7c1581a4dd35a7e1f67dd6 0.881190876000 1312160 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": 858016, "vin": [ { "gen": { "height": 858006 } } ], "vout": [ { "amount": 881190876, "target": { "key": "2048d7fd3475edb8f62cf9b4912270cfd011e41c0b7c1581a4dd35a7e1f67dd6" } } ], "extra": [ 1, 183, 68, 111, 170, 207, 3, 169, 203, 121, 48, 91, 53, 45, 81, 0, 134, 3, 41, 147, 110, 180, 233, 33, 51, 198, 73, 241, 88, 78, 94, 224, 130, 2, 17, 0, 0, 0, 6, 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