Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4fac4fbdb40bd40bb0aa48b7e3a0bcf61b71fe41b1ac843564755f7bb32a60f

Tx prefix hash: b4dc825acac1c8a9cfafd0aeb66ddb92a592203863b9c5ab076cb07c9aba3cb1
Tx public key: 8c2e332066c03326749905909726e31409a40a8fa50ccd2907d646692c43455b
Timestamp: 1697324815 Timestamp [UCT]: 2023-10-14 23:06:55 Age [y:d:h:m:s]: 01:190:12:58:45
Block: 869770 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 397215 RingCT/type: yes/0
Extra: 018c2e332066c03326749905909726e31409a40a8fa50ccd2907d646692c43455b02110000000133af99f4000000000000000000

1 output(s) for total of 0.805547138000 dcy

stealth address amount amount idx
00: 6ac54cc08e15ceed47338912b100308f8dfb526c5876b343543be82620a78092 0.805547138000 1324625 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": 869780, "vin": [ { "gen": { "height": 869770 } } ], "vout": [ { "amount": 805547138, "target": { "key": "6ac54cc08e15ceed47338912b100308f8dfb526c5876b343543be82620a78092" } } ], "extra": [ 1, 140, 46, 51, 32, 102, 192, 51, 38, 116, 153, 5, 144, 151, 38, 227, 20, 9, 164, 10, 143, 165, 12, 205, 41, 7, 214, 70, 105, 44, 67, 69, 91, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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