Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f04834ae2d40ceeeaa56d03beeee61c9e0334e9747e48fb27ef9ac847df93a4

Tx prefix hash: 5eef2503c7c2c369c7e718a5dff17d27d098f7ef4b03c1cb537dfb9dea71ba70
Tx public key: 9297ee9a04f46c2843f471af81ae49d6ee0d265c1097e393853691657190efbf
Timestamp: 1583451556 Timestamp [UCT]: 2020-03-05 23:39:16 Age [y:d:h:m:s]: 04:333:01:25:54
Block: 77044 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1132392 RingCT/type: yes/0
Extra: 019297ee9a04f46c2843f471af81ae49d6ee0d265c1097e393853691657190efbf0211000000054ac5aa02000000000000000000

1 output(s) for total of 340.974608803000 dcy

stealth address amount amount idx
00: ed43f89419c22d57f79d062dee9ed5276812043e5f3227b1eb0e1a916b47bff3 340.974608803000 141861 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": 77054, "vin": [ { "gen": { "height": 77044 } } ], "vout": [ { "amount": 340974608803, "target": { "key": "ed43f89419c22d57f79d062dee9ed5276812043e5f3227b1eb0e1a916b47bff3" } } ], "extra": [ 1, 146, 151, 238, 154, 4, 244, 108, 40, 67, 244, 113, 175, 129, 174, 73, 214, 238, 13, 38, 92, 16, 151, 227, 147, 133, 54, 145, 101, 113, 144, 239, 191, 2, 17, 0, 0, 0, 5, 74, 197, 170, 2, 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