Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47c760554897d2d67137a190a746c918be4783feecac10dc8892c17dadac0f74

Tx prefix hash: fb8094defa2a30a2d53a4b2328b2dbe9a880d832f35d6327c3de2c970dce01a2
Tx public key: eb48397a4e7221329d6ed4de8e9a41e59c39b7493a94eef9b3d343504e447a23
Timestamp: 1712936237 Timestamp [UCT]: 2024-04-12 15:37:17 Age [y:d:h:m:s]: 01:221:16:41:46
Block: 998971 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 417142 RingCT/type: yes/0
Extra: 01eb48397a4e7221329d6ed4de8e9a41e59c39b7493a94eef9b3d343504e447a230211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fb4da972db1e6854169f2bb958860f5850d4952b9fe075b1f43667e15aa57075 0.600000000000 1459447 of 15

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": 998981, "vin": [ { "gen": { "height": 998971 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb4da972db1e6854169f2bb958860f5850d4952b9fe075b1f43667e15aa57075" } } ], "extra": [ 1, 235, 72, 57, 122, 78, 114, 33, 50, 157, 110, 212, 222, 142, 154, 65, 229, 156, 57, 183, 73, 58, 148, 238, 249, 179, 211, 67, 80, 78, 68, 122, 35, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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